Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add removal reason to EntityRemoveFromWorldEvent #11779

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

TonytheMacaroni
Copy link
Contributor

Supercedes #10149.

@TonytheMacaroni TonytheMacaroni requested a review from a team as a code owner December 23, 2024 05:10
@kennytv
Copy link
Member

kennytv commented Dec 23, 2024

Tests fail, you might have to update it to check for our event cause instead. you can also now remove the // Paper comments inside of source files, and for those lines that had a CB comment only from adding the event cause, you can replace their comment with ours

@kennytv kennytv added the type: feature Request for a new Feature. label Dec 23, 2024
@TonytheMacaroni TonytheMacaroni force-pushed the removal-reason branch 2 times, most recently from e203dd4 to 9092ebb Compare December 24, 2024 05:37
@TonytheMacaroni
Copy link
Contributor Author

TonytheMacaroni commented Dec 24, 2024

Re-added the missing test file diff; seems I missed it when updating the PR. Modified the comments. Also moved the usage of Entity#moonrise$getChunkStatus to the Moonrise feature patch.

@kennytv kennytv added the priority: high This issue is either a gamebreaking bug or crash and needs to be addressed soon. label Dec 24, 2024
Copy link
Member

@Machine-Maker Machine-Maker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the Cause enum, I think the 2 booleans should be removed and just be made booleans on the event itself. I don't like tying those to the removal reason. What if a removal reason can be used in 2 places where those values should be different. I don't see much benefit tying them together instead of just putting them on the event itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high This issue is either a gamebreaking bug or crash and needs to be addressed soon. type: feature Request for a new Feature.
Projects
Status: Changes required
Development

Successfully merging this pull request may close these issues.

3 participants